This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: Err .. ~Naomi Deskroterakol 29.Nov.03 05:55 AM a Web browser Applications Development 6.0.2 CF2Windows 2000
Indeed. I had assumed (we all know the dangers of that) that GetNthDocument would suffer the same problem, since the call actually enumerates all the way to the passed number in the collection each time it's called. So doing a GetNthDocument(1000) is considerably more expensive than GetNthDocument(1). But apparently the enumeration isn't a problem, since there are still valid pointers in the collection, that just now reference deletion stubs.
Anyway, no big deal. GetNthDocument is just something to be avoided as far as I'm concerned. But it looks like this is a decent reason to use it, if it avoids the annoying need to reference two document handles when using GetNextDocument.